-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support auto-setting AWS credentials for storage options #78
Support auto-setting AWS credentials for storage options #78
Conversation
cfbc44f
to
14e4c93
Compare
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #78 +/- ##
==========================================
- Coverage 74.06% 71.62% -2.44%
==========================================
Files 6 6
Lines 320 356 +36
==========================================
+ Hits 237 255 +18
- Misses 83 101 +18 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's probably best if tests don't rely on external resources. They'll just end up brittle or skipped for most folks. Given how well defined the S3 API is I think mocking is a good approach here.
Will close #72
Also fix #74 along the way.
@mrocklin, I haven't added tests for this yet. I'm curious if you prefer integration type tests doing actual S3 writes to a protected bucket, so we could add some limited credentials here for like the
s3://dask-deltalake-ci
bucket. Or if you think mocking it is okay.